I did some updates, it now shows one more number and all of them a bit more compressed, hopefully still understandable and meaningful. In time I'll try to add some picture showing LFSW servers and people as well as Airio FREE/FULL servers and people...
The LFS graph is really strange currently it shows almost 1000 people online, while there are less than 700 on all the servers. Either there's 300 more on hidden servers (but usually such do not connect to master, so I have my doubts), or there's something wrong with the count...
The LFS graph is really strange currently it shows almost 1000 people online, while there are less than 700 on all the servers. Either there's 300 more on hidden servers (but usually such do not connect to master, so I have my doubts), or there's something wrong with the count...
Check http://stats.airio.eu/PPL.aspx, see if that's what you were asking for... The page is not linked properly yet to navigation, but the data should be correct. I'll try to think of some more interesting info to show.
Good idea about using joined server to guess the licence. The Web site is downloading server data so it may (hopefully) see what is S0/1/2 server. I'll keep (try to, I mean) the idea in mind and see if some new database table could be used to store people, their licences, and last joined time/date. From this number of unique S0/1/2 people for specified past period could be extracted easily.
PS: In fact the site downloads complete data of all servers every minute, which contain all you're interested in, so the whole system may very well be Airio-independent...
PS: In fact the site downloads complete data of all servers every minute, which contain all you're interested in, so the whole system may very well be Airio-independent...
Exactly, I let it run for a day without limit, but it proved out to be pointless to store below 100 indexes. We'll see, in time the limit may be raised to 150 or even 200...
That's a tough call. As far as I know, the information about s0/s1/s2 licence of specific people is not readily available using LFS World. (I was asking more than a year ago for this info to be added, but...) Airio makes simple assumption that anyone under 8 PBs on LFSW is demo, anyone over the count is licensed. But even this (partially unreliable) info is not sent anywhere, so Autio currently has no info available concerning licence status.
An option would be to use the LFSEI updating, but then the counts will include only people on FULL/PROS Airios and everyone with hidden LFSW stats would be excluded. Another option would be to make Airio update sending guessed S-statuses together with other server data. Uff, sounds rather complicated...
The table used to be in-memory only, so it was erased on each ASP.NET application reset (at least once a day) and the number of items was artificially limited to 1000.
Last week, as I gained more experience, I turned the in-memory table to a database table. That means the table is persistent and there's no real limit concerning the number of entries.
To keep the rubbish out only people with LFSEI higher than 100 are stored.
You mean to generate some graph similar to the one shown under Home icon on LFS World?
Calculating the experience index is relatively expensive concerning the number of requests that need to be processed. For each driver on server three separate tables must be downloaded from LFSW on connect, each LFSW PB improvement, or regularly every 20 minutes (newly 30 minutes). The data needs to be processed, a request to airio.eu formed and sent. The site must then crunch all the available data, do the calculations, store it, and send results back.
Limiting all this to FULL/PROS version has two effects: 1) It is quite probable the server owner knows Airio reasonably well and is able to configure communication properly, because he/she already spent some not negligible amount of money to get the system. 2) The number of requests directed to airio.eu is limited to make sure I do not exceed the allocated server processing time, bandwidth, and database size.
For these reasons, especially the 2nd one, I'm not for now considering processing requests from FREE Airios. There is very similar situation concerning processing of best/good laps (standard cars) and world records/good laps/personal bests (custom cars), limited to PROS Airio versions.
Currently there is no global Airio ban list. Several times I was considering implementing such functionality, but always too many security issues appeared. But the main problem is: Who will be able or allowed to put entries into such a list? Every PROS owner? I'm afraid we all have too different views on who should be banned and what actions deserve a kind of "global" ban. But if you have a workable idea, global Airio ban list could indeed be useful, because certainly some people deserve such a smack.
I did a small update, now all cars with intake air restriction lower than 5% are considered standard cars and the times are stored in the best laps table, if the required criteria are kept (clean lap, 2% within the current best lap). The restriction used in these "extended standard" cars is not stored and not displayed anywhere.
AIRW could require XR2 to add 10 kgs as well, I can change it at any time, but then all (well, most of them) the current XR2 WRs and hotlaps will fall out of XR2 category and new data will have to be gathered.
GT3 car definitions have been added to the Airio World (AIRW) database. They have intake air defined as requested, that is FZ3 = FZR + 28 % + 0 kg, XR3 = XRR + 34 % + 0 kg, FX3 = FXR + 32 % + 0 kg. I did some testing using GT2 and GT3 cars and it seems all data are stored and recalled correctly and properly. You can check some data for example here.
Note 1: For GT3 data to be stored on AIRW you need Airio PROS 2.4.2 (or newer, when available). GT3 cars do not have to be configured locally in Airio and GT3 WRs and good laps will still be stored/shown using AIRW.
Note 2: However, local definitions of GT3s will make sure certain info is locally shown and stored correctly. If adding GT3 definitions to the TCD file make sure they are BEFORE GT2 definitions, or cars will not be recognized properly.
Below you have correct definition of all custom cars supported currently by AIRW. Check this all out, let me know if something fails miserably.
Note 1: For GT3 data to be stored on AIRW you need Airio PROS 2.4.2 (or newer, when available). GT3 cars do not have to be configured locally in Airio and GT3 WRs and good laps will still be stored/shown using AIRW.
Note 2: However, local definitions of GT3s will make sure certain info is locally shown and stored correctly. If adding GT3 definitions to the TCD file make sure they are BEFORE GT2 definitions, or cars will not be recognized properly.
Below you have correct definition of all custom cars supported currently by AIRW. Check this all out, let me know if something fails miserably.
CustomCars=FZ3|FZR,28,0 FZ2|FZR,20,0 XR3|XRR,34,0 XR2|XRR,24,0 FX3|FXR,32,0 FX2|FXR,23,0 XFX|XFG,20,0 XRX|XRG,20,0 FBX|FBM,20,0 UFB|UFR,45,0 FJR|FO8,20,70
Last edited by EQ Worry, .
We could try, it is supposed to work, but it is at the same time a bit tricky matter, having two (or more) custom cars from one standard car... But I'll try to add these definitions and test everything.
One note concerning custom cars. In Airio the restrictions used to get into stats with some custom car are not stored. That means if you rename some custom car, you will lose all stats (unless you do manual car rename in STA.CR file with Airio turned off). If you use different restrictions for custom car of the same name, stats will be mixed.
Autio works differently, it always stores standard car and air/mass restrictions, reconstructing custom cars from these three data whenever necessary. It requires more space and processing, but the advantage is higher flexibility, easy car renaming and introduction or adjustments of car categories.
Well, it needs testing, but again, it is supposed to work. (Which of course means it will not work...) Give me a day to define and test GT3s.
Indeed, but it was done on a below-average notebook by today's standard, 4 years old 2GHz Pentium-M. But on the other hand not everything was exported, only about half of all the available data. Also SQLite is currently used only for export, not as the core stats engine (as LFS Lapper has it, if I remember correctly). But it is just a first step, in time the situation may be reversed and SQLite be used as the primary storage while STA files only as export. Using real database could (hopefully) substantially speed up internal searching and sorting algorithms and simplify the code.
One other note, the www.airio.eu pages are now using a different colors. Also they changed names and are part of ASP.NET now (ASPX instead of HTML file extensions). Old links will also work for some time, but later the HTML files will be completely removed. Links in my signature point to the new structure...
Last edited by EQ Worry, .
Well, when I was adding the command some 18 months ago, maybe I had some reason to hide it as too admin-specific. But I guess you're right and it is not necessary to hide other connected server statuses.
Go to www.lfsworld.net, sign in using your web credentials. Open Racers & hosts online, switch to Insim relay tab, enter IP, insim port, and admin pass of your server(s)... Indeed this has nothing to do with either Lapper or Airio.
Yes, indeed, FJR is also supported, exactly by the mentioned specification. Furthermore there are restricted demo cars, which (maybe) can make LFS more interesting even for demo people... They are XFG, XRG, and FBM, all restricted by 20%...
Great! Thanks for your responses, so the restrictions can stay, which is good. What is also defined is 45% for UFB, but I believe that is a pretty much standard that does not have to be balanced with other cars. Note that you can use such cars on any Airio 2.4.2+ PROS server, whether the cars are defined there or not. But having them defined ensures some special Airio commands will work reliably also with custom cars.
So far it seems it all works reliably. The question is what restrictions of the GT2 cars to use. Currently it stands like this: FZ2 (20%), FX2 (23%), XR2 (24%). We should find good and definite values soon. It will not be possible to have the three cars perfectly balanced, but at least the same balance as with GTR cars should be achieved. As the system works, it is basically possible to move restrictions up and down, but moving it up to higher percentage means many of the already recorded data will be excluded. Well... 
The question is what restrictions of the GT2 cars to use. Currently it stands like this: FZ2 (20%), FX2 (23%), XR2 (24%). We should find good and definite values soon. It will not be possible to have the three cars perfectly balanced, but at least the same balance as with GTR cars should be achieved. As the system works, it is basically possible to move restrictions up and down, but moving it up to higher percentage means many of the already recorded data will be excluded. Well... In my view, there's no need to feel sad and abandoned. You made a strong mark in LFS, for many months being clearly the most popular server around, whatever anyone else is saying, this is a fact. Everyone knew this will end one day, it always does, for various reasons.
I'm not going to comment on the "copying" note, everyone with PROS Airio has the same features available and talking about stealing multiclass racing idea is a bit too wide. But certainly no one can miss a striking similarity of some things, CG could be a bit more inventive.
I realize my views do not matter much, but there were things I personally considered strange at IHR and there were things, that, if changed in time, could save it, maybe still can.
For me the most depressing thing was the extra long time for any update to be in effect. I created a new Airio with much better multiclass support, things people racing at IHR were asking for. It took about 2 months to have that version finally online, while Dave had it running the next hour. That situation still persist, IHR has Airio 2.3.9, while the current version is 2.4.2. And it is not cosmetic changes inside, there are completely new things (such as the Airio World, AIRW).
From my perspective, and I never had/seen any crasher problems at IHR, but then maybe I'm a scary guy, the many many extra long bans were wrong. Extra long bans teach nothing, they only enrage people. We use them rarely even in demo, and only for really wild characters. IHR team was giving them quite often even for minor problems. This approach has seriously backfired, as you can also see in this thread.
The last drop, again my view only, was setting the minimum LFSEI requirement. I know I took part in making such setting available, but you must have seen how many people are not allowed to race at all. And, believe it or not, average and below average drivers make the server populated, the fast and experienced join and stay only if the average are around. Calls for creating pro-like servers, either using time limit or LFSEI, repeatedly fail. So the LFS beginners went to the other server, because there was no limit, even TBO cars available to start with, and they stayed there, drawing others.
My conclusion, and ignore it or laugh about it, as you please: To keep going you need to be dynamic, change fast in response to positive and negative trends, know the system, be able to apply everything without delay, listen to people, use bans to teach and not to infuriate. The CG owner is doing that and I'm always glad to add new options he needs, as I was adding options you needed (but then waited for too long to see them in effect). Well.
Not everything is lost, IHR can be reborn. Try starting again. Update, improve config, cancel bans, think of something new, whatever. Good news for IHR: CG is now a team... and that is a sure way to the ultimate oblivion
, everyone should know it will come one day. I like multiclass racing (though not many can understand that), it would be great to see two cool MC servers running again. Good luck!Airio World
You should not miss this new announcement/tool.
AUTIO - online AIRW and server data
Hi everyone!
In addition to Airio (LFS server tool) and Aonio (LFS client tool) a new LFS feature is finally complete and ready to be presented. It is a set of Web scripts, database tables, and pages showing various statistics and data. I call it Autio and it includes both static (only regularly updated) data from certain Airio-powered servers, and dynamic (always up-to-date) information.
The static part of Autio has been in existence for some months already. It simply allows online browsing through certain servers stats as are usually available using commands such as !sb, !pb, !ptt, !ptc, and dozens of others. The dynamic part is very new and most of the text below concerns only this new part.
Just a few quick links to get an idea what this is about. First static things:Complete AA demo servers stats; Standings in Genuine Racing GTI/TBO series; Best WE1+FOX lap times on FragMaster. And some dynamic data: Current highest LFS Experience Indexes; Best clean online BL1+FBM laps; My current stats in custom cars.
As many people probably have noticed, recently there are new messages on Airio PROS powered servers appearing, starting with AIRW and reporting some lap time improvements or standings. I've been very busy making adjustments to the whole idea, but I consider it now basically complete so the time has come to explain what it is and why it is.
You all know what it is LFS World, LFSW. The Airio World, which the AIRW stands for, is in no way trying to compete with the huge LFSW database. It is simply adding things that are missing in the LFSW and that may help to have more fun, new and more targets to aim for. AIRW consists in essence of three parts.
1) Full support for custom cars. For many years there are certain restricted cars used in LFS, yet they never received "official" support. Examples are GT2 cars (restricted FXR, XRR, FZR) and the very popular UFB (heavily restricted UFR). Some time ago Airio added local support for custom cars, which from then can have separate local statistics. AIRW is basically moving the statistics to global level.
If someone is using a supported custom (restricted) car, data of each lap are sent to airio.eu server, processed, stored in a database, sometimes also response message is sent back. The Web server keeps a database of personal best laps on each track in every custom car. Such laps just need to be complete, cutting and pushing is ignored, improvements are reported back with time difference. This is very similar to what online LFSW improvements do and show.
In addition "clean" laps in custom cars are evaluated separately. Clean lap is one in which the car was always seen by the LFS server/local Airio inside defined path (no grass) and also the car was driving basically alone for the whole lap, there was no other car close by for a prolonged period. This second check/condition excludes all drafting and pushing. Times of clean laps are stored separately and the best of them is current world record (WR) valid for certain custom car on certain track.
Local Airios are getting back information about personal and world records in custom cars and existing commands showing such info from LFSW will show also data from AIRW. That means !pr ufb or !prs fx2 or !wr ufb so1 are perfectly valid commands that will use data coming from AIRW (if such are already available). This full support of custom cars is what I consider the more important part of the AIRW databases.
2) Support for best online hotlaps. This is a feature added on request and the aim is to make online hotlapping somehow more attractive. The BL (best lap) database includes data about unrestricted (standard) cars, but only about clean laps in such cars. Read above to see what is a clean lap (on the path, no cars near).
It keeps/reports only times withing 2% of the current best online clean lap. If there is a BL improvement, records outside the 2% are removed. If someone makes a clean lap and improves his time a message is sent back showing his current position in the BL database and also total records in that particular track/car combo.
I hope showing such data publicly will prove to be a good thing that will make some people proud or happy and others constantly trying to improve. Also I hope online hotlapping may get more popular. It is almost impossible to do clean laps on a packed server, especially multiclass, because there'll be always someone near making the lap invalid. But there is quite a lot other empty servers where hotlappers could go and show their abilities. Such servers could attract more attention and maybe become known and popular even among general community. I must note however that to have the AIRW features the server must run Airio PROS version 2.4.2 or newer.
3) Web interface showing the lap times. Data about custom cars are available online, in Airio, using such commands as !wrs or !prs. Data about best laps are available using !bl and !bls. But there is also a Web interface where you can go through current records and maybe see your positions or go for a possible improvements.
AIRW data are part of Autio site, which anyone can access at stats.airio.eu. BL time tables include both standard and custom cars, in case of custom cars the top time is current "official" WR. PB tables include only custom cars. There is also a link to LFS Experience Index table, now stored as a true database and not just temporary table resetting itself occasionally.
Well, that's about it, welcome to AIRW. I hope you will like it and I must repeat that the point is not to compete with LFSW, which is a much more professional matter. The point is to add new and missing things in an attempt to move LFS again one small step ahead while there is no other visible development concerning tracks, cars, general LFS user experience.
As always, comments and suggestions are most welcome. I was thinking about making this announcement only in the main Airio thread, but the message/explanation got so big I considered a separate new thread more suitable. One last note: Only time will show how much is the service reliable and useful. After all, it includes remote communication that may fail for various reasons. Also bugs may still appear, in scripts, database tables, and in Airio itself. Enjoy!
In addition to Airio (LFS server tool) and Aonio (LFS client tool) a new LFS feature is finally complete and ready to be presented. It is a set of Web scripts, database tables, and pages showing various statistics and data. I call it Autio and it includes both static (only regularly updated) data from certain Airio-powered servers, and dynamic (always up-to-date) information.
The static part of Autio has been in existence for some months already. It simply allows online browsing through certain servers stats as are usually available using commands such as !sb, !pb, !ptt, !ptc, and dozens of others. The dynamic part is very new and most of the text below concerns only this new part.
Just a few quick links to get an idea what this is about. First static things:Complete AA demo servers stats; Standings in Genuine Racing GTI/TBO series; Best WE1+FOX lap times on FragMaster. And some dynamic data: Current highest LFS Experience Indexes; Best clean online BL1+FBM laps; My current stats in custom cars.
As many people probably have noticed, recently there are new messages on Airio PROS powered servers appearing, starting with AIRW and reporting some lap time improvements or standings. I've been very busy making adjustments to the whole idea, but I consider it now basically complete so the time has come to explain what it is and why it is.
You all know what it is LFS World, LFSW. The Airio World, which the AIRW stands for, is in no way trying to compete with the huge LFSW database. It is simply adding things that are missing in the LFSW and that may help to have more fun, new and more targets to aim for. AIRW consists in essence of three parts.
1) Full support for custom cars. For many years there are certain restricted cars used in LFS, yet they never received "official" support. Examples are GT2 cars (restricted FXR, XRR, FZR) and the very popular UFB (heavily restricted UFR). Some time ago Airio added local support for custom cars, which from then can have separate local statistics. AIRW is basically moving the statistics to global level.
If someone is using a supported custom (restricted) car, data of each lap are sent to airio.eu server, processed, stored in a database, sometimes also response message is sent back. The Web server keeps a database of personal best laps on each track in every custom car. Such laps just need to be complete, cutting and pushing is ignored, improvements are reported back with time difference. This is very similar to what online LFSW improvements do and show.
In addition "clean" laps in custom cars are evaluated separately. Clean lap is one in which the car was always seen by the LFS server/local Airio inside defined path (no grass) and also the car was driving basically alone for the whole lap, there was no other car close by for a prolonged period. This second check/condition excludes all drafting and pushing. Times of clean laps are stored separately and the best of them is current world record (WR) valid for certain custom car on certain track.
Local Airios are getting back information about personal and world records in custom cars and existing commands showing such info from LFSW will show also data from AIRW. That means !pr ufb or !prs fx2 or !wr ufb so1 are perfectly valid commands that will use data coming from AIRW (if such are already available). This full support of custom cars is what I consider the more important part of the AIRW databases.
2) Support for best online hotlaps. This is a feature added on request and the aim is to make online hotlapping somehow more attractive. The BL (best lap) database includes data about unrestricted (standard) cars, but only about clean laps in such cars. Read above to see what is a clean lap (on the path, no cars near).
It keeps/reports only times withing 2% of the current best online clean lap. If there is a BL improvement, records outside the 2% are removed. If someone makes a clean lap and improves his time a message is sent back showing his current position in the BL database and also total records in that particular track/car combo.
I hope showing such data publicly will prove to be a good thing that will make some people proud or happy and others constantly trying to improve. Also I hope online hotlapping may get more popular. It is almost impossible to do clean laps on a packed server, especially multiclass, because there'll be always someone near making the lap invalid. But there is quite a lot other empty servers where hotlappers could go and show their abilities. Such servers could attract more attention and maybe become known and popular even among general community. I must note however that to have the AIRW features the server must run Airio PROS version 2.4.2 or newer.
3) Web interface showing the lap times. Data about custom cars are available online, in Airio, using such commands as !wrs or !prs. Data about best laps are available using !bl and !bls. But there is also a Web interface where you can go through current records and maybe see your positions or go for a possible improvements.
AIRW data are part of Autio site, which anyone can access at stats.airio.eu. BL time tables include both standard and custom cars, in case of custom cars the top time is current "official" WR. PB tables include only custom cars. There is also a link to LFS Experience Index table, now stored as a true database and not just temporary table resetting itself occasionally.
Well, that's about it, welcome to AIRW. I hope you will like it and I must repeat that the point is not to compete with LFSW, which is a much more professional matter. The point is to add new and missing things in an attempt to move LFS again one small step ahead while there is no other visible development concerning tracks, cars, general LFS user experience.
As always, comments and suggestions are most welcome. I was thinking about making this announcement only in the main Airio thread, but the message/explanation got so big I considered a separate new thread more suitable. One last note: Only time will show how much is the service reliable and useful. After all, it includes remote communication that may fail for various reasons. Also bugs may still appear, in scripts, database tables, and in Airio itself. Enjoy!
In case there's still some confusion, AllowJoining indeed controls just repeated joining. That means you can set NumRejoins to 0, which basically says midrace join is not allowed, except for people with AllowJoining or higher limad level.
Registration is a manual process of specifying RName items (per server) of people maybe registered for some event. AllowRegister would then ignore registration requirement again for some higher limads.
Registration is a manual process of specifying RName items (per server) of people maybe registered for some event. AllowRegister would then ignore registration requirement again for some higher limads.
There are tools (such as the TC Admin Panel or Fire Daemon) that indeed see stopped (closed) applications (in Airio after !quit) as crashed and restart them. But you need to close Airio correctly (and not simply kill it), otherwise data loss may happen. Solution is simple:
1) Open Airio.cfg.txt file.
2) Set StopExit=true.
3) Restart Airio or type !rld if it is already running.
Then after !quit Airio will be closed down properly, but it will stay running (and will not be restarted by service management applications) in a suspended state and then you may safely kill it using TC panel...
PS: Thanks, Dean, for update!
1) Open Airio.cfg.txt file.
2) Set StopExit=true.
3) Restart Airio or type !rld if it is already running.
Then after !quit Airio will be closed down properly, but it will stay running (and will not be restarted by service management applications) in a suspended state and then you may safely kill it using TC panel...
PS: Thanks, Dean, for update!
Yup, I was releasing new Airio and Aonio at the same time and got lost a bit in all the numbers... 
Thanks!
Existují vyšší verze, FULL a PROS, ty jsou za peníze... Sice se mi nikdy nevrátí, co jsem investoval, ale občas něco přijde a to velmi potěší.
That is a weird thing, because as we tested, if I use the same data my Airio connects without problems. I'm really lost. Only one wild idea: Try changing instance name in CFG file to something without a space. Uhm, but I do not think that is the cause...
Oops, 1.3.5 is correct... Announcement post edited...
Airio 2.4.1
Airio 2.4.1 is released and available for download and update. Very soon I'll be sending the update also to Franky of 500servers, then it should be available there as service update.
FREE: This update contains mostly corrections of some previously existing inconsistencies, but also separate display of online (!pr) and offline (!hl) personal records, as well as new configuration items to specify what race join checks are ignored from what limad level.
FULL: There is a new !hls command showing summary of all uploaded hotlaps. Similarly to !prs (showing online best laps) you may limit the display to certain tracks/cars/both. In !pl output newly a two-letter countrycode of individual drivers is shown in light blue color (if available and recognized).
PROS: This version contains probably the most important and interesting update, simple (for now) support of data storing similar to LFS World, but concerning specific custom cars, which are standard cars with restrictions (air intake, additional mass). The database is called AIR World, AIRW for short. Every lap finished in a restricted car is sent to airio.eu and stored/updated in a database. If a defined custom car is recognized a message announcing new AIRW personal best (PB) can be returned and displayed on server. Completely clean laps (no grass, always on the strictest proper path) go also to hotlaps table and new best times in recognized cars are reported back as new AIRW world records (WR). Both personal (online and hotlap) and global (WR on each stored track/car combo) tables are returned on request in a format mimicking the one used by LFSW, downloaded by Airio and combined with LFSW data. This means all data commands such as !pr, !prs, !hls, !wr will recognize custom car types and display corresponding real data, not just recalculated values as before. For more info see Airio changelog. If this addition proves to be reliable and usable, it may be extended.
As usual, it is not possible to check all the updates in every detail and under every possible configuration, so any reports concerning troubles with 2.4.1 are welcome. Otherwise, enjoy!
FREE: This update contains mostly corrections of some previously existing inconsistencies, but also separate display of online (!pr) and offline (!hl) personal records, as well as new configuration items to specify what race join checks are ignored from what limad level.
FULL: There is a new !hls command showing summary of all uploaded hotlaps. Similarly to !prs (showing online best laps) you may limit the display to certain tracks/cars/both. In !pl output newly a two-letter countrycode of individual drivers is shown in light blue color (if available and recognized).
PROS: This version contains probably the most important and interesting update, simple (for now) support of data storing similar to LFS World, but concerning specific custom cars, which are standard cars with restrictions (air intake, additional mass). The database is called AIR World, AIRW for short. Every lap finished in a restricted car is sent to airio.eu and stored/updated in a database. If a defined custom car is recognized a message announcing new AIRW personal best (PB) can be returned and displayed on server. Completely clean laps (no grass, always on the strictest proper path) go also to hotlaps table and new best times in recognized cars are reported back as new AIRW world records (WR). Both personal (online and hotlap) and global (WR on each stored track/car combo) tables are returned on request in a format mimicking the one used by LFSW, downloaded by Airio and combined with LFSW data. This means all data commands such as !pr, !prs, !hls, !wr will recognize custom car types and display corresponding real data, not just recalculated values as before. For more info see Airio changelog. If this addition proves to be reliable and usable, it may be extended.
As usual, it is not possible to check all the updates in every detail and under every possible configuration, so any reports concerning troubles with 2.4.1 are welcome. Otherwise, enjoy!
FGED GREDG RDFGDR GSFDG